release: prepare 0.2.0 - #21
Merged
Merged
Conversation
A minor rather than a patch: the release adds the target-first form and the Grok Build adapter, and removes --untrusted. Also clears the one thing standing between a tag and a published release. Releases are gated on CI, and CI has been red on main since before either of the last two merges: gosec reads `args[i+1:]` and `args[:i]` in parseFlags as possibly out of range, when i is an index obtained by ranging over args and both slices are in range by construction. gosec does not follow that through the reassignment of args, so the finding is annotated with its reason rather than the parser being reshaped for a linter on the eve of a release. The changelog's 0.2.0 section is also put back into Keep a Changelog order. Merging #20 left a Fixed block ahead of Added and a second Fixed block after Removed; they are now one Fixed section in the conventional position. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PuwaXDJut6CorENbW1KHPk
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version constant to
0.2.0, changelog[Unreleased]stamped as[0.2.0] - 2026-08-22.Minor, not patch. The release adds the target-first form (
reach <target> <command>) and the Grok Build adapter, and removes--untrusted.Also here, because the tag will not publish without it
Releases are gated on CI —
release.ymlcallsci.ymlas a reusable workflow and publishes nothing until all of it is green. CI has been red on main since before the last two merges, on two gosec findings inparseFlags:Both are false.
iis an index obtained by ranging overargs, soargs[i+1:]andargs[:i]are in range by construction; gosec does not follow that through the reassignment ofargsin the loop body. Annotated with the reason, in the style the repo already uses inshim.goandcache.go, rather than reshaping an argument parser to satisfy a linter on the eve of a release.golangci-lint run ./...now reports0 issues.Changelog ordering
Merging #20 left the 0.2.0 section with a
### Fixedblock ahead of### Addedand a second### Fixedafter### Removed. They are now a single Fixed section in Keep a Changelog order, and the release gets a lead paragraph in the style of 0.1.1.Checks
go build,go vet,go test ./...,golangci-lint run ./...all clean locally.reach versionreportsreach 0.2.0.Once this is green and merged,
v0.2.0gets tagged on main.🤖 Generated with Claude Code
https://claude.ai/code/session_01PuwaXDJut6CorENbW1KHPk